Method for synthesizing mobile identification numbers

ABSTRACT

A method for adding functionality to a network system is provided. The method is particularly applicable to network systems that utilize a limited number of data packets, e.g., Mobile Identification Numbers (MINs), to send instructions between the network operations center and the individual devices coupled to the network operations center. The added functionality is achieved by assigning more than one function or possible response to at least some of the secondary MINs and allowing secondary MINs to be combined.

CROSS-REFERENCES TO RELATED APPLICATIONS

[0001] This application is a continuation-in-part of U.S. patentapplication Ser. Nos. 09/347,389, 09/547,270, 09/547,272, and09/837,738, the specifications of which are incorporated herein in theirentirety for any and all purposes.

FIELD OF THE INVENTION

[0002] The present invention relates generally to systems forcommunicating via a wireless network to selected devices and, moreparticularly, to a method of synthesizing secondary MobileIdentification Numbers (MINs) for use in a communication system.

BACKGROUND OF THE INVENTION

[0003] A variety of different types of systems utilize a centralizedcommunications to monitor, remotely operate, and otherwise communicatewith remote devices. For example, many home and vehicle security systemsuse a variety of monitors (e.g., door, window, floor pressure, motion,sound, smoke detectors, etc.) that are coupled via a wireless network toa centralized office. In general, the centralized office is staffedaround the clock so that when a critical event occurs (e.g., break-in,burglary, fire, etc.) the monitored event can be reported to thesuitable parties (e.g., police department, fire department, propertyowner, etc.).

[0004] Unfortunately, there are a number of problems associated withtypical monitoring systems. First, it can be difficult to continuallyupdate the monitoring service as conditions, such as contact informationfor the property owner, change. Not only can it be difficult to changesuch information, the information intake service personnel may makemistakes, leading to the service being unable to locate the propertyowner in an emergency. Second, the monitoring personnel can makemistakes with respect to a reported incident, for example not noting theoccurrence of an event, improperly reporting or delaying the reportingof the event, etc.

[0005] For a variety of reasons, typically the problems associated withcentralized and staffed monitoring services are more severe in vehiclemonitoring systems. First, it is generally more important to notify theuser in the case of a monitored vehicle alarm than it is for a homealarm since there is a higher likelihood of receiving a false, andeasily corrected, alarm in the former case. Accordingly, the ability toeasily and reliably update contact information becomes more critical forvehicle monitoring systems. Second, the user is more likely to wish toremotely and periodically determine the status of their car (e.g., inmotion, travel speed, location, door/window conditions, etc.) than theirhome, thus requiring a simpler, user-friendlier interface than thatassociated with a staffed operations center. Third, the delay inherentin a staffed monitoring system is particularly problematic with respectto vehicles due to their inherent mobility, and thus the speed by whichthey can be vandalized and/or stolen. Fourth, the user is more likely towish to alter the monitoring conditions associated with their car thanthose associated with their home, adding to the desire for an easier andmore reliable interface. Fifth, the costs associated with a staffedmonitoring system are typically too excessive to allow the level ofcontrol and monitoring that may be desired by the vehicle's owner.

[0006] One solution to the afore-mentioned problems is an automatedsystem that allows the user to communicate with, receive informationfrom, and otherwise control a remotely located device without requiringany interaction or interference from system personnel. Such an automatedsystem can utilize any of a variety of communication networks, althoughpreferably a wireless, bidirectional network is used. An example of sucha network is that provided by Aeris.net™.

[0007] In a network system such as the Aeris.net™ system, data packetsare sent over standard cellular control channels, thereby bypassing thevoice channel. There are two types of control channels and messagetypes: Forward Control Channels (FOCC) or downstream messages andReverse Control Channels (RECC) or upstream messages. FOCC or downstreammessages utilize data packets comprised of Mobile Identification Numbers(MINs). A typical network system is designed to support a limited numberof MINs per device. For example, the Aeris.net™ system supports a totalof 11 MINs per device, a primary MIN and 10 secondary MINs. Thesecondary MINs, each of which identifies a specific remote device, canbe used to elicit various functions from the identified remote device.As one of the secondary MINs is reserved for use by the network and thecellular system operator, there are a total of 9 secondary MINsavailable for use in such a system.

[0008] Although 9 secondary MINs are sufficient for many applications,some monitoring systems would benefit from the added functionalityoffered by additional secondary MINs. Unfortunately, increasing thenumber of offered secondary MINs would significantly impact the designand cost of the network system.

[0009] Accordingly, what is needed in the art is a method for addingfunctionality to a system utilizing a limited number of data packets perdevice, e.g., secondary MINs. The present invention provides such asystem.

SUMMARY OF THE INVENTION

[0010] The present invention provides a method for adding functionalityto a network system, specifically one that utilizes a limited number ofdata packets, e.g., Mobile Identification Numbers (MINs), to sendinstructions between the network operations center and the individualdevices coupled to the network operations center. The addedfunctionality is achieved by assigning more than one function orpossible response to at least some of the secondary MINs and allowingsecondary MINs to be combined.

[0011] In at least one embodiment of the invention, one or moresecondary MINs are defined to be Command Sequence Triggers or CSTs.During use, when a remote device receives a non-CST secondary MIN, itimmediately responds according to the pre-assigned instruction for thereceived non-CST secondary MIN. If, however, the remote device receivesa CST secondary MIN, it initiates a timer rather than immediatelyresponding. If another secondary MIN is received within a pre-definedperiod of time, the remote device responds on the basis of thecombination of the first and second secondary MINs. If another secondaryMIN is not received within the pre-defined time period, the remotedevice responds on the basis of the single CST secondary MIN. Thus theCST secondary MIN is given, in this embodiment, two different meaningsdepending upon whether or not it is combined with another secondary MIN.

[0012] In at least one other embodiment of the invention, the system isprogrammed to allow the receipt of more than one CST secondary MIN. Thusif the remote device receives a first CST secondary MIN and thenreceives a second CST secondary MIN within the pre-defined time period,it does not respond immediately, rather it waits to determine if a thirdsecondary MIN follows the second secondary MIN. If a third secondary MINis received within the pre-defined time period, the remote devicedetermines the pre-assigned response which corresponds to thecombination and sequence of the first, second and third secondary MINs.The system can be configured to allow a maximum number of iterations orto allow an unlimited number of iterations. The system can also beconfigured to either require a predetermined number of secondary MINs inorder to respond or to simply respond on the basis of the total numberof received secondary MINs, the total number based only on secondaryMINs received within the pre-allotted time periods.

[0013] In at least one other embodiment of the invention, CST secondaryMINs cannot be combined with non-CST secondary MINs. Preferably in thisembodiment the total number of CST secondary MINs that can be acceptedby the remote device is limited. Also preferably in this embodiment aminimum number of CST secondary MINs must be received prior to theremote device responding. Alternately, rather than requiring a minimumnumber of CST secondary MINs, the remote device can be configured torespond on the basis of the CST secondary MINs received during theallotted time period.

[0014] In at least one other embodiment of the invention, everysecondary MIN is treated as a CST secondary MIN. Accordingly, afterreceipt of a first secondary MIN, the remote device initiates a timer.If a second secondary MIN is not received within a pre-allotted timeperiod, the remote device responds on the basis of the first secondaryMIN. If a second secondary MIN is received within the pre-allotted timeperiod, depending upon the configuration of the system, the remotedevice either responds on the basis of the combination of the first andsecond secondary MINs or it re-initiates the timer and again waits forthe receipt of another secondary MIN. In order to control the responsetime, preferably this embodiment is limited to the receipt of twosecondary MINs, i.e., a first and a second secondary MIN, thus allowingthe remote device to respond immediately upon receipt of the secondsecondary MIN.

[0015] A further understanding of the nature and advantages of thepresent invention may be realized by reference to the remaining portionsof the specification and the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0016]FIG. 1 is an illustration of an embodiment of an automated usernotification system constructed in accordance with the presentinvention;

[0017]FIG. 2 is an illustration of one embodiment of a remote device inaccordance with the present invention;

[0018]FIG. 3 illustrates the methodology associated with sending anaction request utilizing Aeris.net™ or a similar system;

[0019]FIG. 4 illustrates the methodology associated with sending a wildcard utilizing Aeris.net™ or a similar system;

[0020]FIG. 5 illustrates an embodiment of the invention in which thefunctionality of the network system is expanded by assigning one or moresecondary MINs as Command Sequence Triggers or CSTs;

[0021]FIG. 6 illustrates an embodiment of the invention in which CSTsecondary MINs are not combinable with non-CST secondary MINs;

[0022]FIG. 7 illustrates an embodiment of the invention in which everysecondary MIN is treated as a CST secondary MIN; and

[0023]FIG. 8 illustrates an embodiment of the invention in which atleast one secondary MIN is reserved for immediate response.

DESCRIPTION OF THE SPECIFIC EMBODIMENTS

[0024]FIG. 1 is an illustration of an embodiment of an automated usernotification system 100 constructed in accordance with the presentinvention. User notification system 100 is comprised of a networkoperations center (NOC) 101, a user interface 103 and a notificationinterface 105. NOC 101 is coupled to a communication network system 107,preferably a bi-directional communication network, and more preferably acommercial bidirectional communication network such as that provide byAeris.net™. NOC 101, via network 107, communicates with a plurality ofremote devices 109. Preferably network 107 provides wirelesscommunication to devices 109 although it is understood that either someor all of the remote devices 109 can be coupled to NOC 101 via a wirednetwork.

[0025] NOC 101 is comprised of a processor 111 and a database 113.Processor 111 controls the functionality of NOC 101, as further outlinedbelow, and may be comprised of a single processor or multipleprocessors. Multiple processors may be used to provide systemredundancy, to interface with the desired number of remote devices 109,and/or to provide dedicated functionality (e.g., responding to userrequests, responding to sensor alerts, billing customers, etc.).Database 113 includes a user database, billing information, responsecodes and instructions, etc. and is preferably comprised of bothvolatile and non-volatile memory.

[0026]FIG. 2 is an illustration of one embodiment of remote device 109.It is understood that system 100 can be comprised of a plurality ofidentical or non-identical devices 109, non-identical devices 109allowing for variations between devices 109 in order to account for userneeds, device location, device mounting configuration, sensor type andnumber, desired device complexity, user interface options, remotefunctionality, network communications, etc. It is understood that eachdevice 109 is attached to a specific, uniquely identifiable vehicle orother property, or a uniquely identifiable portion of a larger article.

[0027] Regardless of the type or desired functionality of device 109,each such device includes a controller 201, typically comprised of aprocessor and a memory module, and a transceiver 203 that allows device109 to communicate via network 107 with NOC 101. In the preferredembodiment of the invention, and assuming that device 109 is coupled toa vehicle (e.g., car, boat, plane, motorbike, etc.) or other relativelymobile apparatus, the device also includes a global positioning system(GPS) module 205. In general, transceiver 203 and GPS module 205 willutilize separate antennae, 207 and 209 respectfully, although it will beappreciated that both modules can utilize a single antenna.

[0028] In the preferred embodiment, device 109 includes one or moresensors 211 which can sense a variety of conditions relating to thevehicle to which it is attached. For example, sensors 211 may includemotion sensors, door sensors (e.g., door opened/closed), door locksensors, window sensors (e.g., window opened/closed), car roof status(e.g., convertible up/down, sun-roof opened/closed), light sensors(e.g., lights on/off), engine status sensors, speed sensors, occupantsensors (e.g., pressure sensors located within the vehicles seats), etc.Sensors 211 may also utilize an Intelligent Data Base or IDB. The IDB isa peer to peer data network available for use in automotive devices andother ground vehicles which has access to important vehicle systems,such as the vehicle's electrical system and components. Sensors 211 mayalso utilize an On-Board Diagnostic system or OBD. The OBD systemprovides a means of diagnosing engine problems and controlling enginefunctions.

[0029] In the preferred embodiment, device 109 includes one or moredevice controllers 213. Controllers 213 can be used to control variousfunctions of the systems to which they are attached. For example,controllers 213 can be used to remotely lock/unlock doors, close/openwindows, close/open convertible top, close/open sun-roof, turn on/offlights, enable/disable engine, enable/disable ignition switch, activatea cellular phone within the passenger compartment of the vehicle, etc.

[0030] In at least one embodiment of the invention, device 109 includesa local interface 215. Local interface 215 is preferably comprised of akeypad or other switching means. Additionally, local interface 215preferably includes one or more indicators, visual, audible, or both.Local interface 215 can be used to control the status of device 109(e.g., on/off), allow for local emergency activation (e.g., panicswitch), and/or allow for direct user/NOC communications (e.g., for userrequested directions, addresses, telephone numbers, etc.).

[0031] In at least one embodiment of the invention, device 109 includesone or more localized alarms 217 which can be activated prior to,simultaneously with, or after a notification alert or other message issent to NOC 101 by device 109. Alarms 217 can include a separate horn orother sounding device or alarm 217 can simply activate the vehicle'shorn. Additionally, alarms 217 can include a relay switch coupled to thelights, thus allowing for the activation of some or all of the vehicle'slights, either continuously or intermittently.

[0032] Device 109 can interact with NOC 101 in a variety of ways and inresponse to a variety of conditions. Once notified of a specificcondition, NOC 101 can notify the user, police, fire department,paramedics, or other parties based on the preprogrammed notificationinstructions contained within NOC 101. Additionally, NOC 101 can beconfigured to send a response directly to device 109 (e.g., disableengine, honk horn, flash lights, lock doors, determine and send positioncoordinates, etc.). A few examples of system operational modes areprovided below although it will be appreciated that these are only meantas examples and that there are other uses for the disclosed system.

[0033] Alarm mode: Preferably system 100 is configured to provide alarmfunctionality. Specifically, device 109 is preferably configured tonotify NOC 101 whenever there is an occurrence of a predetermined alarmevent (e.g., vehicle break-in, vehicle movement, fire, etc.). Sensors211 detect the alarm event, for example by monitoring the condition ofthe doors, windows, engine, ignition switch, seat pressure, vehiclemovement (e.g., speed or positional changes), engine tachometer, smokedetectors, CO₂ detectors, etc.

[0034] Notification mode: System 100 can be configured to notify NOC 101upon the occurrence of a specific condition. For example, the user mayset-up the system to send a notification message whenever the vehicleexceeds a predetermined speed or leaves a predetermined geographicregion. Alternately, the system can be configured to send a responseimmediately upon the occurrence of the specified condition. For example,if device 109 includes an external rain sensor, when rain is sensed andNOC 101 is notified of the rain, the system can automatically directdevice 109 to close all vehicle windows, convertible top, sun-roof, etc.Alternately, the system can be configured to send a response to thelocal system and notify the user immediately upon the occurrence of thespecified condition. For example, if a sensor within device 109determines that the vehicle to which device 109 is attached is exceedinga predetermined speed, the system can notify the user and also directdevice 109 to employ a speed limiter.

[0035] NOC 101, through notification interface 105, is configurable andprogrammable to utilize a variety of different notification devices, thenotification devices allowing communication with end users (e.g.,notifying an end user that an alarm condition has been detected). In thepreferred embodiment, NOC 101 automatically responds to a preprogrammedcondition or occurrence (e.g., a detected alarm condition on a specificdevice 109), thereby not requiring human operator instructions or otherhuman interaction. Accordingly, in the preferred embodiment, interface105 is coupled to electronic mail (i.e., e-mail), facsimile, pagerand/or standard telephonic devices. In order to utilize standardtelephonic devices in the preferred automated system, interface 105includes a voice synthesis system. Additionally interface 105 of thepreferred embodiment is coupled to a public data network, such as theInternet, thus allowing notification messages to be sent by e-mail aswell as through page updates on a secure, user-accessible WEB site.

[0036] User interface 103, coupled to NOC 101, allows end users toaccess and control the operation of NOC 101. In the preferredembodiment, interface 103 allows at least limited user/NOCcommunications without the need for a human operator. Preferablyinterface 103 is coupled to the Internet, thus allowing user access viae-mail and/or WEB site manipulation. Additionally, interface 103 can becoupled to a telephone system. In order to allow automated operation,the telephone system preferably includes a voice recognition systemalthough a simple tone recognition system can also be used. Preferablysystem 100 is configured to allow users, through user interface 103, toobtain status information about a user item to which a device 109 iscoupled (e.g., determine if the doors are locked), to enable/disablespecific sensors 211, to control specific subsystems of the vehicle towhich device 109 is attached (e.g., door locks), to reprogram aspects ofdevice 109, to revise notification instructions, to revise contactinformation, to revise sensor alarm conditions, to obtain billinginformation, etc., all without the need for human operator assistance.

[0037] As previously disclosed, the present invention can utilize bothwireless and wired communication channels. In the preferred embodiment,a wireless system is used in which the data flowing between NOC 101 anddevices 109 (e.g., detected events, status checks, equipment control,etc.) is sent as data packets over existing cellular networks. In onepreferred embodiment, network system 107 is comprised of the Aeris.net™network and the data packets are sent using the Aeris.net™ MicroBurst®technology. It will be appreciated that other technologies can be usedto send and receive the data packets of the present invention. Forexample, VBurst® technology can be used with the Aeris.net™.Alternately, the present invention can utilize the control channel ofthe AMPS analog cellular phone system for the communication link betweenremote devices 109 and NOC 101. Other alternate wireless communicationsystems include the GSM cell phone system which supports SMS (i.e.,short message service) for the bidirectional delivery of data; theMobitex™ data message delivery system offered in the Erricson and BellSouth systems; the Ricochet™ brand of data transceivers offered byMetricom; and other cellular systems supporting such formats as the CDPDstandard of wireless messaging. Satellite based wireless systems such asthe ORBCOM™ system by Orbital Sciences Corporation can also be used tolink remote devices 109 to NOC 101. Wired communication channels includeanalog phone lines, ISDN phone lines, T1 phone lines, and DSL phonelines. An alternate to any of the public carrier systems is a privatedata network.

[0038] As the above-identified communication systems are well known,including the preferred Aeris.net™ system, a detailed description of therequired controllers, data routers, firmware, standardized protocols,etc. is not provided herein. It is understood, however, that transceiver203 and controller 201 of each device 109 includes the necessaryfirmware/software to achieve compatibility with network 107 (e.g.,receive, decode and execute instructions originating at NOC 101, codeand transmit information for use by NOC 101, etc.).

[0039] In a typical network system such as the Aeris.net™ system used inthe preferred embodiment, the data packets are sent over standardcellular control channels, thereby bypassing the voice channel. Thereare two types of control channels and message types: Forward ControlChannels (FOCC) or downstream messages, which operate from the NOC 101to a remote device 109, and Reverse Control Channels (RECC) or upstreammessages, which operate from the remote device 109 back to NOC 101. Inthe preferred embodiment, each upstream message is comprised of a15-digit word with each digit being comprised of a 4-bit nibble of range1 to A (hex). Upstream messages are described in further detail inco-pending U.S. Patent applications Ser. Nos. 09/347,389, filed Jul. 6,1999, 09/547,270, filed Apr. 11, 2000, 09/547,272, filed Apr. 11, 2000,and 09/837,738, filed Apr. 17, 2001. These applications are incorporatedherein by reference in their entirety for any and all purposes.

[0040] FOCC or downstream messages utilize data packets comprised ofMobile Identification Numbers (MINs). In a typical network system 107,such as the Aeris.net™ system, each remote device 109 along with thenetwork system is designed to support a total of 11 MINs per device, aprimary MIN and 10 secondary MINs. The secondary MINs, each of which areassigned to a specific remote device 109, can be used by NOC 101 toelicit various functions from the assigned remote device 109. As one ofthe secondary MINs is reserved for use by the network and the cellularsystem operator, there are a total of 9 secondary MINs available for useby NOC 101.

[0041] Table I below provides an example of possible uses for thesecondary MINs in a system in which remote devices 109 are coupled tocars. It is understood that the indicated actions are only meant asexamples: other instructional sets can be designed and implemented.Additionally it is understood that although the secondary MIN in Table Iis abbreviated as a number from 1 to 10, in actuality the secondary MINis comprised of a sequence of digits. Accordingly it is the sequence ofdigits that corresponds to the abbreviated secondary MIN to which aspecific device 109 responds. Therefore even though every device 109includes a fourth secondary MIN, secondary MIN #4 for one device 109will be different from the secondary MIN #4 for every other device 109,thus allowing a specific device from a plurality of remote devices 109to respond to the received secondary MIN. TABLE I Secondary MIN Action 1Disarm the alarm system 2 Arm the alarm system 3 Unlock the doors 4 Lockthe doors 5 Report vehicle location using on-board GPS system 6 Disableignition switch 7 Sound horn, disable ignition switch, flash lights,start continuous GPS reporting 8 Initiate continuous GPS reporting 9Send ACK (acknowledgement) in response to message from car 10 Reservedfor Aeris net ™ use

[0042]FIG. 3 illustrates the methodology associated with sending anaction request utilizing Aeris.net™ or a similar system. Initially NOC101 sends an instruction (step 301) via network 107 that all remotedevices 109 receive. One remote device 109, the device that has beenprogrammed to respond to the transmitted secondary MIN, responds (step303) while the other remote devices 109 ignore the secondary MIN (step305).

[0043] Given the limitations imposed by having only 9 availablesecondary MINs, network system 107 provides a method of obtainingadditional functionality for those users requiring such additionalfunctionality. The method utilizes “wild card” MINs that the system user(e.g., NOC system operator) purchases, typically in blocks, from thenetwork system operator. In this approach one of the secondary MINs foreach remote device 109 is programmed as a wild card alert MIN. Forexample, as shown in Table II, secondary MIN 9 has been reserved as awild card alert MIN. Thus when NOC 101 transmits a wild card alert (step401 of FIG. 4), all remote devices 109 ignore the alert (step 403)except for the remote device with a secondary MIN matching that of thetransmitted wild card alert (step 405). The alerted device then acceptsthe next wild card secondary MIN that NOC 101 transmits (step 407), thusnot requiring a match between the transmitted action and any of thesecondary MINs of the intended device 109. TABLE II Secondary MIN Action1 Disarm the alarm system 2 Arm the alarm system 3 Unlock the doors 4Lock the doors 5 Report vehicle location using on-board GPS system 6Disable ignition switch 7 Sound horn, disable ignition switch, flashlights, start continuous GPS reporting 8 Initiate continuous GPSreporting 9 Wild card alert 10 Reserved for Aeris.net ™ use

[0044] As a result of the wild card system of designating secondaryMINs, a remote device 109 can respond to a virtually unlimited number ofsecondary MINs even though it may recognize a significantly fewer numberof secondary MINs (e.g., 8 user programmed actions plus the wild cardalert secondary MIN). There are several advantages to this approach.First, it allows a remote device to respond to hundreds of secondaryMINs, and thus NOC initiated instructions, while recognizing a verylimited number of secondary MINs. Second, network system 107 does notneed to expend resources (eg., system memory) for end users that do notrequire a greater instructional set than that allowed for by the baseset (e.g., recognition of 9 user-specified secondary MINs with theAeris.net™ system). Third, the complexity of remote devices 109 can bethey only need the ability to recognize a very limited number ofsecondary primary disadvantage of this approach is that the systemoperator (e.g., NOC 101) must purchase a block of wild cards, thussignificantly adding to system operating costs can be especiallyproblematic in many systems in which the additional instructions/actionsallowed by the use of the wild cards are infrequently required or if thesystem operator only needs to supply a few additionalinstructions/actions.

[0045] In an alternate method of expanding the functionality of anetwork system such as Aeris.net™, the present invention assigns one ormore secondary MINs as a Command Sequence Trigger or CST. One or moreCSTs can be used to dramatically number of instructions/actions that canbe transmitted by NOC 101 to a designated device 109 without requiringthe purchase of wild cards from network operator 107.

[0046] In use, and as illustrated in FIG. 5, NOC 101 initially transmitsa CST to a designated remote device 109 (step 501). The CST secondaryMIN is ignored by all non-intended remote devices 109 (step 503). Theintended remote device 109 recognizes the transmitted CST secondary MINand initiates a timer (step 505). If the designated remote device 109does not receive an additional secondary MIN within a predetermined timeperiod (step 507), it responds to the CST secondary MIN as preprogrammed(step 509). In the preferred embodiment of the invention, thepredetermined time period is 60 seconds although it is understood thatthis time period can be shorter or longer without departing from theinvention. If no additional secondary MIN is received within theallotted time, the designated device can be programmed to simply ignorethe CST secondary MIN or to perform a specific action (e.g., activatethe horn, send a request for additional instructions to NOC 101, etc.).If an additional secondary MIN is received within the allotted time(step 511), the designated remote device performs the actioncorresponding to the combination of the CST secondary MIN and theadditional secondary MIN (step 513). Alternately, remote device 109 canbe programmed to determine if the additional secondary MIN is anotherCST secondary MIN (step 515). If the additional secondary MIN is notanother CST secondary MIN (step 517), then the device performs theaction corresponding to the combination of the CST secondary MIN and theadditional secondary MIN (step 518). If the additional secondary MIN isanother CST (step 519), then the device can either respond on the basisof the combination of the first and second CST secondary MINs (step 520)or, in an alternate embodiment, initiate the timer and begin waiting forreceipt of another secondary MIN (step 521). If an additional secondaryMIN is received within the allotted time (step 523), the designatedremote device performs the action corresponding to the combination ofthe first CST instruction, the second CST instruction, and theadditional secondary MIN (step 525). If no additional secondary MIN isreceived within the allotted time (step 527), the designated remotedevice performs the action corresponding to the combination of the firstand second received CST secondary MINs (step 529). In the embodimentillustrated in FIG. 5, the system is limited to a total of threesecondary MINs. Thus even if all three secondary MINs are CSTs (e.g., 9,8, 9), the system would not wait to determine if an additional secondaryMIN will be received after receipt of the third CST before responding.It is understood, however, that this limitation is an artificiallimitation used to limit the response delay of remote device 109. Thesame system could be configured to enter the waiting loop (i.e., steps507 or 521 of FIG. 5) every time that the received secondary MIN is aCST. In the above example, this configuration would allow the device torespond to the receipt of secondary MINs such as 8, 9, 9, 8, 8, 1.Additionally it should be understood that although FIG. 5 onlyillustrates the use of two CST secondary MINs, the system can beprogrammed to permit the designation of more than two CST secondaryMINs, thus adding further flexibility to the system.

[0047] Table III illustrates the use of CSTs according to an embodimentof the present invention. It is understood that the instructions/actionsprovided are only meant as examples of possible actions and thatdifferent actions as well as fewer/greater numbers of CSTs orfewer/greater numbers of total allowed secondary MINs can be utilizedwithout departing from the invention. TABLE III Secondary MIN Action 1Disarm the alarm system 2 Arm the alarm system 3 Unlock the doors 4 Lockthe doors 5 Report vehicle location using on-board GPS system 6 Disableignition switch 7 Sound horn, disable ignition switch, flash lights,start continuous GPS reporting 8 CST - If no additional secondary MINsreceived within allotted time, lower windows 9 CST - If no additionalsecondary MINs received within allotted time, raise windows 10 Reservedfor Aeris.net ™ use 8 + 1 Activate mobile phone 8 + 2 Deactivate mobilephone 8 + 3 Raise convertible roof 8 + 4 Lower convertible roof 8 + 5Close sun-roof 8 + 6 Open sun-roof 8 + 7 Activate speed monitor 8 + 8Activate speed monitor and report if the speed exceeds 40 mph 8 + 9Activate speed monitor and report if the speed exceeds 50 mph 9 + 1Activate speed monitor and report if the speed exceeds 60 mph 9 + 2Activate speed monitor and report if the speed exceeds 70 mph 9 + 3Activate speed monitor and report if the speed exceeds 80 mph 9 + 4Activate speed monitor and report if the speed exceeds 90 mph 9 + 5Activate speed monitor and report vehicle location when speed exceeds 40mph. Continue to report location every 5 minutes until speed drops below40 mph. 9 + 6 Activate speed monitor and report vehicle location whenspeed exceeds 50 mph. Continue to report location every 5 minutes untilspeed drops below 50 mph. 9 + 7 Activate speed monitor and reportvehicle location when speed exceeds 60 mph. Continue to report locationevery 5 minutes until speed drops below 60 mph. 9 + 8 Activate speedmonitor and report vehicle location when speed exceeds 70 mph. Continueto report location every 5 minutes until speed drops below 70 mph. 9 + 9Activate speed monitor and report vehicle location when speed exceeds 80mph. Continue to report location every 5 minutes until speed drops below80 mph. 8 + 8 + 1 Initiate continuous GPS monitoring, report locationevery 1 minute 8 + 8 + 2 Initiate continuous GPS monitoring, reportlocation every 2 minutes 8 + 8 + 3 Initiate continuous GPS monitoring,report location every 3 minutes 8 + 8 + 4 Initiate continuous GPSmonitoring, report location every 5 minutes 8 + 8 + 5 Initiatecontinuous GPS monitoring, report location every 10 minutes 8 + 8 + 6Initiate continuous GPS monitoring, report location every 15 minutes 8 +8 + 7 Initiate continuous GPS monitoring, report location every 20minutes 8 + 8 + 8 Initiate continuous GPS monitoring, report locationevery 30 minutes 8 + 8 + 9 Initiate continuous GPS monitoring, reportlocation every 45 minutes 8 + 9 + 1 Initiate continuous GPS monitoring,report location every 60 minutes 8 + 9 + 2 Initiate continuous GPSmonitoring, report location every 120 minutes 8 + 9 + 3 Initiatecontinuous GPS monitoring, report location every 180 minutes 8 + 9 + 4Initiate continuous GPS monitoring, report location every 240 minutes8 + 9 + 5 Activate location monitor and report if vehicle goes furtherthan 0.1 miles from present location 8 + 9 + 6 Activate location monitorand report if vehicle goes further than 0.25 miles from present location8 + 9 + 7 Activate location monitor and report if vehicle goes furtherthan 0.5 miles from present location 8 + 9 + 8 Activate location monitorand report if vehicle goes further than 1 mile from present location 8 +9 + 9 Activate location monitor and report if vehicle goes further than5 miles from present location 9 + 8 + 1 Activate location monitor andreport if vehicle goes further than 10 miles from present location 9 +8 + 2 Activate location monitor and report if vehicle goes further than20 miles from present location 9 + 8 + 3 Activate location monitor andreport if vehicle goes further than 30 mile from present location 9 +8 + 4 Activate location monitor and report if vehicle goes further than40 miles from present location 9 + 8 + 5 Activate location monitor andreport if vehicle goes further than 50 miles from present location 9 +8 + 6 Activate location monitor and report if vehicle goes further than75 miles from present location 9 + 8 + 7 Activate location monitor andreport if vehicle goes further than 100 mile from present location 9 +8 + 8 Activate location monitor and report if vehicle goes further than250 miles from present location 9 + 8 + 9 Activate location monitor andreport if vehicle goes further than 500 miles from present location 9 +9 + 1 Activate location monitor and report if vehicle goes further than750 miles from present location 9 + 9 + 2 Activate location monitor andreport if vehicle goes further than 1000 miles from present location 9 +9 + 3 Report vehicle status using OBD system 9 + 9 + 4 Flash lights andpulse horn for 10 seconds (to help locate car in parking lot) 9 + 9 + 5Flash lights and pulse horn for 30 seconds (to help locate car inparking lot) 9 + 9 + 6 Activate on-board cell phone and call presetnumber to allow passenger compartment monitoring 9 + 9 + 7 Pulse horn,flashlights, start continuous GPS reporting 9 + 9 + 8 Activate seatpressure sensors 9 + 9 + 9 Acknowledge NOC instruction receipt

[0048] As illustrated by the example of Table III, in at least onepreferred embodiment of the invention, the order that secondary MINs,including CSTs, are received by a device 109 will determine the courseof action. Thus in the above example the receipt of secondary MINs inthe order 9, 8, and then 2 will result in the intended device 109performing a different action than the receipt of the same secondaryMINs in the order 8, 9, and then 2.

[0049] In an alternate embodiment, the CST secondary MINs are notcombinable with any non-CST secondary MINs. Preferably the number of CSTsecondary MINs that can be received by a remote device 109 is limited.Thus, for example, in the embodiment shown in FIG. 6, the system isconfigured to require the receipt of three CST secondary MINs beforeresponding. The invention can also be configured to require either feweror greater numbers of CST secondary MINs.

[0050] As illustrated, after the intended remote device 109 receives afirst CST secondary MIN (step 505), it initiates a timer (step 601).Assuming that the system has been configured as described, if noadditional CST secondary MINs are received within the allotted time(step 603), the system resets (step 605). If a second CST secondary MINis received (step 607), the system restarts the timer with the same ordifferent amount of time allotted for response (step 609). If a thirdCST secondary is not received within the allotted time (step 611), thesystem resets, otherwise the remote device 109 responds on the basis ofthe combination of the three CST secondary MINs. Table IV indicates thepossible secondary MIN combinations along with exemplarinstructions/actions for this embodiment TABLE IV Secondary MIN Action 1Disarm the alarm system 2 Arm the alarm system 3 Unlock the doors 4 Lockthe doors 5 Report vehicle location using on-board GPS system 6 Disableignition switch 7 Sound horn, disable ignition switch, flashlights,start continuous GPS reporting 8 CST 9 CST 10 Reserved for Aeris.net ™use 8 + 8 + 8 Activate mobile phone 8 + 8 + 9 Deactivate mobile phone8 + 9 + 8 Report vehicle status using OBD system 8 + 9 + 9 Flash lightsand pulse horn for 10 seconds (to help locate car in parking lot) 9 +8 + 8 Initiate continuous GPS monitoring, report location every 5minutes 9 + 8 + 9 Activate location monitor and report if vehicle goesfurther than 1 mile from present location 9 + 9 + 8 Activate speedmonitor and report if the speed exceeds 40 mph 9 + 9 + 9 Activate speedmonitor and report vehicle location when speed exceeds 40 mph. Continueto report location every 5 minutes until speed drops below 40 mph.

[0051] In an alternate embodiment, rather than resetting the device ifadditional CST secondary MINs are not received (i.e., steps 603 and611), the device can be configured to respond on the basis of the CSTsecondary MINs received. Thus in the above example, after step 603 theremote device would respond on the basis of the single received CSTsecondary MIN. Similarly, after step 611 the remote device would respondon the basis of the first and second CST secondary MINs.

[0052] In an alternate embodiment, every secondary MIN is treated as aCST secondary MIN. As illustrated in FIG. 7, in this embodiment as inthe prior embodiment, after NOC 101 transmits a secondary MIN (step701), all non-intended remote devices 109 ignore the transmittedsecondary MIN (step 703) while the intended remote device 109 recognizesand accepts the secondary MIN (step 705). The intended remote device 109then initiates a timer and, for a preset time (e.g., 60 seconds), waitsfor the receipt of an additional secondary MIN (step 707). If theintended remote device 109 does not receive an additional secondary MINwithin the preset time period, (step 709), it treats the initialsecondary MIN as a single secondary MIN and responds accordingly (step711). If an additional secondary MIN is received within the allottedtime (step 713), the intended remote device restarts the timer utilizingeither the same or a different time period and again waits for thereceipt of an additional secondary MIN (715). If an additional secondaryMIN is not received within the time period (step 717), the intendedremote device 109 performs the action that corresponds to thecombination of the first and second received secondary MINs (step 719).If an additional secondary MIN is received within the allotted time(step 721), then the process of waiting for additional secondary MINsand responding depending upon whether or not additional secondary MINsare received starts over.

[0053] Preferably the process illustrated in FIG. 7 is only permitted aspecific number of iterations, thus limiting the possible delayassociated with the waiting steps (e.g., steps 707 and 715 of FIG. 7).Accordingly, the system could be limited to only accepting a combinationof two secondary MINs, three secondary MINs, etc., before responding.Alternately, and as illustrated in FIG. 7 with step 723, the process canbe permitted to run indefinitely, thus allowing for any combination ofall of the user assignable secondary MINs. The system can be configuredto permit the same secondary MIN to be used only once in a singlesequence or to be used more than once, thus allowing an infinite numberof instructional sequences to be transmitted, assuming the number ofwaiting steps is not limited. As noted in the prior embodiment,preferably the order in which secondary MINs are received is used todistinguish specific requested actions. Accordingly, the receipt ofsecondary MINs 2, 4, 7 in that order will result in the designatedremote device 109 performing a different instruction than if the samesecondary MINs are received in the order 2, 7, 4; 4, 2, 7; 4, 7, 2; etc.

[0054] Although the embodiment illustrated in FIG. 7 allows for a largerinstructional set than the embodiment illustrated in FIGS. 5 or 6, thedisadvantage of this approach is that no instruction is immediatelyperformed since the system always enters into the timer mode afterreceipt of a secondary MIN. Thus, for example, after the intended remotedevice 109 receives the first secondary MIN in step 705, beforeresponding it first waits to determine if a second secondary MIN will bereceived. Even though the delay is short, depending upon the timersetting, the delay may still be longer than desired under certainconditions (e.g., car theft). Accordingly, in an alternate embodiment,at least one secondary MIN is reserved for immediate response. Forexample, as illustrated in FIG. 8 and assuming that secondary MINs 2 and3 have been reserved for immediate response, after the intended remotedevice 109 receives a secondary MIN (step 705), it then determines ifthe received secondary MIN is one requiring immediate attention, i.e.,secondary MIN 2 or 3 (step 801). If the received secondary MINcorresponds to one requiring immediate attention (step 803), remotedevice 109 acts immediately on the basis of the received secondary MIN(step 805). If the received secondary MIN does not correspond to onerequiring immediate attention (step 807), then the system begins theprocess of waiting for additional secondary MINs and respondingaccording to whether or not additional secondary MINs are received asdescribed above in reference to FIG. 7.

[0055] Depending upon how many instructions/actions remote device 109must be capable of responding to, limiting the number of additionalsecondary MINs a remote device 109 will accept can accelerate theprocess in accordance with any of the preceding embodiments. Forexample, the system can be configured to require a remote device 109 toact immediately upon receipt of a second secondary MIN, thus limitingthe delay to the time allotted for waiting for receipt of the secondsecondary MIN after receipt of the initial secondary MIN. Accordingly,after step 511 of FIG. 5 or step 713 of either FIG. 7 or FIG. 8, theremote device would immediately respond rather than entering into anadditional waiting period as illustrated.

[0056] In at least one embodiment of the invention, when a remote device109 receives a secondary MIN it responds with an acknowledgement (ACK)message. If NOC 101 does not receive the appropriate ACK message itresponds in accordance with the system programming, typically byresending the secondary MIN until either the secondary MIN issuccessfully received or until the secondary MIN has been transmitted apredetermined number of times (e.g., 3 times). In at least one otherembodiment of the invention, remote device 109 does not send an ACKmessage until all expected secondary MINs have been successfullyreceived. For example, in the embodiment illustrated in FIG. 6,preferably the intended remote device 109 will not send an ACK messageuntil it has received all three CST secondary messages.

[0057] As will be understood by those familiar with the art, the presentinvention may be embodied in other specific forms without departing fromthe spirit or essential characteristics thereof. Accordingly, thedisclosures and descriptions herein are intended to be illustrative, butnot limiting, of the scope of the invention which is set forth in thefollowing claims.

What is claimed is:
 1. A method of interpreting secondary MobileIdentification Numbers (MINs), the method comprising the steps of:accepting a first secondary MIN by an intended remote device, whereinsaid intended remote device is one of a plurality of remote devicescapable of receiving said first secondary MIN, wherein said firstsecondary MIN is one of a plurality of secondary MINs uniquelyidentifying said intended remote device and distinguishing said intendedremote device from said plurality of remote devices; determining if saidfirst secondary MIN is a first Command Sequence Trigger (CST) secondaryMIN; responding to said first secondary MIN if said first secondary MINis determined not to be said first CST secondary MIN; initializing atimer if said first secondary MIN is determined to be said first CSTsecondary MIN; accepting a second secondary MIN by said intended remotedevice if said second secondary MIN is received by said intended remotedevice within a preset time period as determined by said timer and ifsaid first secondary MIN is determined to be said first CST secondaryMIN, wherein said second secondary MIN is one of said plurality ofsecondary MINs uniquely identifying said intended remote device anddistinguishing said intended remote device from said plurality of remotedevices; and performing a first pre-assigned response, wherein saidfirst pre-assigned response corresponds to the acceptance of both saidfirst and said second secondary MINs by said intended remote device. 2.The method of claim 1, wherein said first pre-assigned response iscomprised of transmitting a status of at least one monitored conditionof a user device coupled to said intended remote device to said networkoperations center.
 3. The method of claim 1, wherein said firstpre-assigned response is comprised of transmitting a set of positioncoordinates to said network operations center, wherein said set ofposition coordinates correspond to a user device coupled to saidintended remote device.
 4. The method of claim 1, wherein said firstpre-assigned response is comprised of instructing a device controllercoupled to said intended remote device to perform a predefined function.5. The method of claim 1, wherein said first pre-assigned response iscomprised of transmitting an acknowledgement message to said networkoperations center.
 6. The method of claim 1, wherein said firstpre-assigned response is comprised of: determining if said secondsecondary MIN is a second CST secondary MIN; performing a secondpre-assigned response if said second secondary MIN is determined not tobe said second CST secondary MIN; initializing said timer if said secondsecondary MIN is determined to be said second CST secondary MIN;accepting a third secondary MIN by said intended remote device if saidthird secondary MIN is received by said intended remote device within asecond preset time period as determined by said timer and if said secondsecondary MIN is determined to be said second CST secondary MIN, whereinsaid third secondary MIN is one of said plurality of secondary MINsuniquely identifying said intended remote device and distinguishing saidintended remote device from said plurality of remote devices; andperforming a third pre-assigned response, wherein said thirdpre-assigned response corresponds to the acceptance of said first,second and third secondary MINs by said intended remote device.
 7. Themethod of claim 6, wherein said second pre-assigned response correspondsto resetting said intended remote device.